-
Notifications
You must be signed in to change notification settings - Fork 2.9k
remove kubelet scrapes for 5k nodes dra job #35844
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remove kubelet scrapes for 5k nodes dra job #35844
Conversation
Signed-off-by: Alay Patel <alayp@nvidia.com>
e42b162 to
b4a8144
Compare
jackfrancis
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alaypatel07, jackfrancis The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@alaypatel07: Updated the
DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
The perf-tests repository, hardcodes prometheus memory to 10Gig if kubelet scrapes are enabled.
This is leading to prometheus pod OOMing. Removing the kubelet scrape will mean the job will not collect driver mertics, but doing that is favorable for now to unblock the 5k test run. In the future there is a need to find a way to collect kubelet metrics without hardcoding prometheus memory to 10 gigs
Ref: #35700 (comment)